home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
IRIX Base Documentation 1998 November
/
IRIX 6.5.2 Base Documentation November 1998.img
/
usr
/
share
/
catman
/
u_man
/
cat1
/
oview_layout.z
/
oview_layout
Wrap
Text File
|
1998-10-20
|
7KB
|
133 lines
OOOOVVVVIIIIEEEEWWWW____LLLLAAAAYYYYOOOOUUUUTTTT((((1111)))) OOOOVVVVIIIIEEEEWWWW____LLLLAAAAYYYYOOOOUUUUTTTT((((1111))))
NNNNAAAAMMMMEEEE
oooovvvviiiieeeewwww____llllaaaayyyyoooouuuutttt - determine CrayLink interconnection topology of Origin
systems
SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
////uuuussssrrrr////ppppccccpppp////bbbbiiiinnnn////oooovvvviiiieeeewwww____llllaaaayyyyoooouuuutttt [----aaaa _a_r_c_h_i_v_e] [----hhhh _h_o_s_t] [----nnnn _p_m_n_s_f_i_l_e]
DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
oooovvvviiiieeeewwww____llllaaaayyyyoooouuuutttt attempts to determine the interconnection topology of Origin
2000 and Origin 200 systems. It is not normally run by users, but rather
invoked automatically from the Origin systems visualization program,
oooovvvviiiieeeewwww(1).
oooovvvviiiieeeewwww____llllaaaayyyyoooouuuutttt contacts the PCP collection daemon ppppmmmmccccdddd(1) on the target
_h_o_s_t (if ----hhhh is given) or accesses the PCP _a_r_c_h_i_v_e (if ----aaaa is given) to
obtain the Craylink interconnection inventory and uses this to resolve
the logical topology of the system.
oooovvvviiiieeeewwww____llllaaaayyyyoooouuuutttt can currently resolve the topology of Origin systems with an
unlimited number of CrayLink routers with logical topologies respresented
by an edge, star, plane, or series of cubes and/or planes.
Planes are chosen from different modules linked to each other by having
their routers connected on the same slots. That is, module A is connected
to module B with routers on slot 1 connected together and routers on slot
2 connected together. Cubes are formed by connected planes. An edge and a
star are degenerate cases handled separately.
If oooovvvviiiieeeewwww____llllaaaayyyyoooouuuutttt successfully resolves the topology of the target host or
archive, it prints it in the following format (identical to the input
format expected by oooovvvviiiieeeewwww(1)).
_rrrr_oooo_uuuu_tttt_eeee_rrrr_::::_MMMM_...._SSSS _XXXX _YYYY _ZZZZ
_llll_iiii_nnnn_kkkk _rrrr_pppp_oooo_rrrr_tttt_::::_MMMM_...._SSSS_...._PPPP _rrrr_oooo_uuuu_tttt_eeee_rrrr_::::_MMMM_...._SSSS
_...._...._....
_llll_iiii_nnnn_kkkk _rrrr_pppp_oooo_rrrr_tttt_::::_MMMM_...._SSSS_...._PPPP _nnnn_oooo_dddd_eeee_::::_MMMM_...._SSSS _[[[[_cccc_pppp_uuuu_::::_MMMM_...._SSSS_...._NNNN _[[[[_cccc_pppp_uuuu_::::_MMMM_...._SSSS_...._NNNN_]]]]_]]]]
_...._...._....
Where M and S denote an Origin 2000 module and slot respectively (a
``slot'' may be either a router slot or a node slot, depending on the
context), P denotes a CrayLink router port number, N denotes a CPU number
(either aaaa or bbbb), and X, Y and Z are coordinates in a Cartesian space.
The keywords _rrrr_oooo_uuuu_tttt_eeee_rrrr, _llll_iiii_nnnn_kkkk, _rrrr_pppp_oooo_rrrr_tttt, _nnnn_oooo_dddd_eeee and _cccc_pppp_uuuu are literals.
In configurations with no router, the router and router port numbers are
negative to indicate their placeholder status.
CCCCAAAAVVVVEEEEAAAATTTTSSSS
For systems which use metarouters (systems with 65 or more processors),
the metarouters are currently ignored, however, the other routers and
links for the system will be shown as normal, i.e. the system layout will
PPPPaaaaggggeeee 1111
OOOOVVVVIIIIEEEEWWWW____LLLLAAAAYYYYOOOOUUUUTTTT((((1111)))) OOOOVVVVIIIIEEEEWWWW____LLLLAAAAYYYYOOOOUUUUTTTT((((1111))))
be a series of cubes but with no links between the cubes (these are the
meta-router links).
If the CrayLink interconnections have not been properly configured, then
oooovvvviiiieeeewwww____llllaaaayyyyoooouuuutttt may become confused.
FFFFIIIILLLLEEEESSSS
////vvvvaaaarrrr////ppppccccpppp////ppppmmmmnnnnssss////*
default local PMNS specification files
////vvvvaaaarrrr////ppppccccpppp////ccccoooonnnnffffiiiigggg////ppppmmmmllllooooggggggggeeeerrrr////ccccoooonnnnffffiiiigggg....oooovvvviiiieeeewwww____llllaaaayyyyoooouuuutttt
ppppmmmmllllooooggggggggeeeerrrr(1) configuration file suitable for use with oooovvvviiiieeeewwww____llllaaaayyyyoooouuuutttt
SSSSEEEEEEEE AAAALLLLSSSSOOOO
ddddkkkkvvvviiiissss(1), mmmmppppvvvviiiissss(1), nnnnooooddddeeeevvvviiiissss(1), oooovvvviiiieeeewwww(1), PPPPCCCCPPPPIIIInnnnttttrrrroooo(1), ppppmmmmaaaaffffmmmm(1), ppppmmmmccccdddd(1),
ppppmmmmiiiieeee(1), ppppmmmmiiiinnnnffffoooo(1), ppppmmmmllllooooggggggggeeeerrrr(1), ppppmmmmttttiiiimmmmeeee(1), ppppmmmmvvvvaaaallll(1), ppppmmmmvvvviiiieeeewwww(1),
rrrroooouuuutttteeeerrrrvvvviiiissss(1), XXXX(1), eeeennnnvvvviiiirrrroooonnnn(5) and ppppmmmmllllaaaauuuunnnncccchhhh(5).
PPPPaaaaggggeeee 2222